Skip to content

refactor!: change raw keyring key_name type to str #292

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Aug 17, 2020

Conversation

MatthewBennington
Copy link
Contributor

Issue #, if available: #284

Description of changes: Change the type of the key_name field to str.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Check any applicable:

  • Were any files moved? Moving files changes their URL, which breaks all hyperlinks to the files.

@MatthewBennington MatthewBennington self-assigned this Aug 13, 2020
Copy link
Member

@mattsb42-aws mattsb42-aws left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor naming change in tests

@@ -32,7 +32,7 @@

_ENCRYPTION_CONTEXT = {"encryption": "context", "values": "here"}
_PROVIDER_ID = "Random Raw Keys"
_KEY_ID = b"5325b043-5843-4629-869c-64794af77ada"
_KEY_ID = "5325b043-5843-4629-869c-64794af77ada"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: for consistency, let's call this _KEY_NAME (and probably rename _PROVIDER_ID to _KEY_NAMESPACE) since they're substantively different now.

ditto in the raw RSA tests

@MatthewBennington
Copy link
Contributor Author

Looks like the check failure is transient, going to re-run checks.

@mattsb42-aws
Copy link
Member

Travis flakiness passed. Merging.

@mattsb42-aws mattsb42-aws merged commit e46b757 into aws:keyring Aug 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants